Customization of data session retry mechanism in a wireless packet data service network

ABSTRACT

In one embodiment, a method is provided for customization of a mobile communications device&#39;s data session retry mechanism in a wireless packet data service network. The mobile communication device requests activation of a data session with a node via the wireless network and receives a reject message via the wireless network in response to the request for activation of the data session, the reject message including a cause code. If the cause code corresponds to a no-retry behavior of the data session retry mechanism of the mobile communication device, the mobile communications device no longer requesting activation of a data session with the node.

CLAIM OF PRIORITY UNDER 35 U.S.C. § 120 & 37 C.F.R. § 1.78

This non-provisional application is a continuation application claimingthe benefit of the following prior United States patent applicationhaving the same title: application Ser. No. 14/666,048, filed Mar. 23,2015, which itself is a continuation of application Ser. No. 13/950,803,filed Jul. 25, 2013, which itself is a continuation of application Ser.No. 12/480,569, filed Jun. 8, 2009, which is itself a continuation ofapplication Ser. No. 10/981,864, filed Nov. 5, 2004 and now issued asU.S. Pat. No. 7,561,891, each of which is hereby incorporated byreference.

FIELD OF THE APPLICATION

The present patent application generally relates to wireless packet dataservice networks. More particularly, and not by way of an limitation,the present patent application is directed to a scheme for customizationof a mobile device's data session retry mechanism in a wireless packetdata service network.

BACKGROUND

Radio resources in a wireless packet data service network are scarce.When a data-centric mobile device continues to negotiate with thenetwork infrastructure for establishing a data session even after itreceives certain reject codes, such repeated attempts can contribute toan increase in the signaling load in the network whereby the overallperformance of the network may be negatively impacted.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the embodiments of the present patentapplication may be had by reference to the following DetailedDescription when taken in conjunction with the accompanying drawingswherein:

FIG. 1 depicts an exemplary network environment including a wirelesspacket data service network wherein an embodiment of the present patentapplication may be practiced;

FIG. 2A depicts additional details of an exemplary wireless packet dataservice network operable with a mobile communications device inaccordance with an embodiment;

FIGS. 2B-2D depict message flow diagrams with respect to varioussignaling procedures utilized in accordance with an embodiment;

FIG. 3 depicts an exemplary list of cause codes operable with thewireless packet data service network shown in FIG. 2A in servicing amobile communications device according to one embodiment;

FIG. 4 depicts an exemplary structure for mapping cause codes of awireless packet data service network to a flag relating to a mobilecommunications device's data session retry mechanism;

FIG. 5 depicts a software architectural view of a mobile communicationsdevice operable to customize its data session retry mechanism accordingto one embodiment;

FIG. 6 depicts a flowchart of an embodiment for customizing data sessionretry operations in a mobile communications device; and

FIG. 7 depicts a block diagram of a mobile communications deviceoperable to customize its data session retry mechanism according to oneembodiment.

DETAILED DESCRIPTION OF THE DRAWINGS

In one aspect, an embodiment of a mobile communications device isdisclosed. The claimed embodiment comprises at least one or more of thefollowing features: means for detecting that a code has been received atthe mobile communications device from an external node; means fordetermining whether the code is identified as a critical code; and meansfor disabling a data session retry mechanism of the mobilecommunications device if the code is identified as a critical code.

In another aspect, an embodiment of a method for controlling a mobilecommunications device is disclosed. The claimed embodiment comprises atleast one or more of the following features: detecting that a code hasbeen received at the mobile communications device from an external node;determining whether the code is identified as a critical code; anddisabling a data session retry mechanism of the mobile communicationsdevice responsive to a determination that the code is identified as acritical code.

In yet another aspect, an embodiment of a network node is disclosed. Theclaimed embodiment comprises at least one or more of the followingfeatures: a structure configured to receive a code; a structureconfigured to query a database to determine whether the code received atthe node is identified in the database as a critical code; and astructure configured to a communicate to a mobile communications devicewhether the code received at the node is identified in the database as acritical code, thereby disabling a data session retry mechanism of themobile communications device if the code is identified in the databaseas a critical code.

A system and method of the present patent application will now bedescribed with reference to various examples of how the embodiments canbest be made and used. Like reference numerals are used throughout thedescription and several views of the drawings to indicate like orcorresponding parts, wherein the various elements are not necessarilydrawn to scale. Referring now to the drawings, and more particularly toFIG. 1, depicted therein is an exemplary network environment 100including a wireless packet data service network 112 wherein anembodiment of the present patent application may be practiced. Anenterprise network 102, which may be a packet-switched network, caninclude one or more geographic sites and be organized as a local areanetwork (LAN), wide area network (WAN) or metropolitan area network(MAN), et cetera, for serving a plurality of corporate users. A numberof application servers 104-1 through 104-N disposed as part of theenterprise network 102 are operable to provide or effectuate a host ofinternal and external services such as email, video mail, Internetaccess, corporate data access, messaging, calendaring and scheduling,information management, and the like. Accordingly, a diverse array ofpersonal information appliances such as desktop computers, laptopcomputers, palmtop computers, et cetera, although not specifically shownin FIG. 1, may be operably networked to one or more of the applicationservers 104-i, i=1, 2, . . . , N, with respect to the services supportedin the enterprise network 102.

Additionally, a remote services server 106 may be interfaced with theenterprise network 102 for enabling a corporate user to access oreffectuate any of the services from a remote location using a suitablemobile communications device (MCD) 116. A secure communication link withend-to-end encryption may be established that is mediated through anexternal IP network, i.e., a public packet-switched network such as theInternet 108, as well as the wireless packet data service network 112operable with MCD 116 via suitable wireless network infrastructure thatincludes a base station (BS) 114. In one embodiment, a trusted relaynetwork 110 may be disposed between the Internet 108 and theinfrastructure of wireless packet data service network 112. By way ofexample, MCD 116 may be a data-enabled handheld device capable ofreceiving and sending messages, web browsing, interfacing with corporateapplication servers, et cetera.

For purposes of the present patent application, the wireless packet dataservice network 112 may be implemented in any known or heretoforeunknown mobile communications technologies and network protocols, aslong as a packet-switched data service is available therein fortransmitting packetized information. For instance, the wireless packetdata service network 112 may be comprised of a General Packet RadioService (GPRS) network that provides a packet radio access for mobiledevices using the cellular infrastructure of a Global System for MobileCommunications (GSM)-based carrier network. In other implementations,the wireless packet data service network 112 may comprise an EnhancedData Rates for GSM Evolution (EDGE) network, an Integrated DigitalEnhanced Network (IDEN), a Code Division Multiple Access (CDMA) network,or any 3^(rd) Generation (3G) network. By way of providing an exemplaryembodiment, the teachings of the present patent application will beillustrated with a GPRS-based carrier network, although those skilled inthe art should readily recognize that the scope of the present patentapplication is not limited thereby.

FIG. 2A depicts additional details of an exemplary wireless packet dataservice network operable with a mobile communications device inaccordance with an embodiment. As illustrated, reference numeral 202refers to a GPRS network operable as the wireless packet data servicenetwork with respect to MCD 116 that is provided with a number ofdata-centric user applications 210 such as, e.g., web browsing, email,multimedia, File Transfer Protocol or FTP, telnet, etc. Base station 114serves MCD 116 via the air interface using applicable radio layerprotocols.

GPRS uses a packet-switching technique to transfer both high-speed andlow-speed data and signaling in an efficient manner over GSM radionetworks. Packet switching means that GPRS radio resources are used onlywhen users are actually sending or receiving data. Rather thandedicating a radio channel to a mobile data user, e.g., MCD 116, for afixed period of time, the available radio channels can be concurrentlyshared between several users. Therefore, GPRS is designed to supportfrom intermittent and bursty data transfers (e.g., web browsing) tooccasional transmission of large volumes of data (e.g., FTP). Allocationof GPRS radio channels can be flexible: from 1 to 8 radio interfacetimeslots can be allocated per one Time Division Multiple Access (TDMA)frame. Typically, timeslots are shared by the active users, and uplinksand downlinks are allocated separately. Various radio channel codingschemes are available to allow a range of data bit transfer rates.

Two additional network nodes are provided within a GSM network in orderto implement a packet-switched data transfer service. A Serving GPRSSupport Node (SGSN) 206, which is coupled to a Home Location Register(HLR) 204 and disposed at the same hierarchical level as a MobileSwitching Center (MSC) of the circuit-switched cellular network, isoperably coupled to BS 114 and keeps track of the location of a GPRSuser such as the user of MCD 116. Further, SGSN 206 is responsible forperforming security functions and handling access control with respectto MCD 116. A Gateway GPRS Support Node (GGSN) 208 provides interworkingwith the external packet-switched IP network 108, and is operablycoupled to one or more SGSNs, e.g., SGSN 206, via an IP-based GPRSbackbone network.

In order to access the packet data service, MCD 116 makes its presenceknown to the network by performing what is known as a GPRS Attach.Thereafter, to send and receive packet data, MCD 116 activates thepacket data address that it wants to use. This operation renders MCD 116“visible” in the corresponding GGSN, and interworking with external datanetworks can then begin. User data is transferred transparently betweenMCD 116 and the external data networks with a method known asencapsulation and tunneling wherein data packets are equipped withGPRS-specific protocol information and transferred transparently betweenMCD 116 and GGSN 208.

To get access to the GPRS network 202 and to start data transmission,various signaling procedures are therefore effectuated before activatinga Packet Data Protocol (PDP) context between MCD 116 and the network.FIGS. 2B-2D depict a plurality of message flow diagrams with respect tovarious signaling procedures utilized in the GPRS network 202 inaccordance with an embodiment. Referring in particular to FIG. 2B, anAttach signaling procedure is described therein. In an Attach procedure,MCD 116 provides its identity, e.g., International Mobile StationIdentity (IMSI), and the type of attach (i.e., GPRS Attach) via anAttach Request message 220 to SGSN 206. Once SGSN 206 obtains theidentity of MCD 116, it retrieves the subscriber information from HLR204. If the subscriber information cannot be found, SGSN 206 will returnan Attach Reject reply message to MCD 116. If the requisite subscriberinformation is found in HLR 204, SGSN 206 accepts the Attach Requestmessage 220 and allocates a new identifier, e.g., Packet-TemporaryMobile Station Identity or P-TMSI, to MCD 116. A Temporary Logical LinkIdentifier (TLLI) is then derived from the P-TMSI received from SGSN206. The derived TLLI will be used by MCD 116 to identify itself forsubsequent signaling or data procedures with the GPRS network.

Accordingly, responsive to the Attach Request message 220, SGSN 206updates HLR 204 with the current location of MCD 116 by sending anUpdate GPRS Location Request message 222. In response, HLR 204 sends thesubscriber information relating to MCD 116 to SGSN 206 through an InsertSubscriber Data Request message 224, which is acknowledged by SGSN 206via an Acknowledge message 226. Thereafter, HLR 204 acknowledgescompletion of update location to SGSN 206 via an Update GPRS LocationAcknowledge message 228. Since appropriate subscriber information hasbeen found in HLR 204, SGSN 206 sends an Attach Accept message 230 witha P-TMSI to MCD 116. In response, MCD 116 returns an Attach Completemessage 232 with a TLLI derived from the P-TMSI to acknowledge thereceipt of the P-TMSI.

After the Attach procedure is successfully executed, MCD 116 enters aReady state whereupon a Mobility Management (MM) context, which is arecord that contains subscriber information and MCD identity, isestablished in both MCD 116 and SGSN 206. Thereafter, MCD 116 mayactivate a PDP context via an Activation signaling procedure forcommunicating with an external data network. FIG. 2C depicts a messageflow diagram with respect to an Activation signaling procedure. MCD 116is operable to specify a Transaction Identifier (TI) and a NetworkService Access Point Identifier (NSAPI) which are used by the GPRSinfrastructure to uniquely identify a data session. In a furtherimplementation, MCD 116 can include an Access Point Name (APN) in themessage, which directs SGSN 206 to select a particular GGSN for use. Byway of example, MCD 116 may send an Activate PDP Context Request message250 with such parameters as TI, NSAPI, APN, Requested Quality of Service(QoS), etc., to SGSN 206. Upon validating the message, SGSN 206 sends aCreate PDP Context Request message 252 to the appropriate GGSN 208 witha Tunnel Identifier (TID) constructed by appending the identity of MCD116 and the NSAPI. GGSN 208 validates the parameters in the Create PDPContext Request message 252 and returns a Create PDP Context Responsemessage 254 with no error code if the Request is accepted. Thereafter,SGSN 206 sends an Activate PDP Context Accept message 256 to MCD 116 toindicate that the requested data session has been activated.

User data coming from the application layer may be encapsulated beforereaching the external packet data network. As shown in FIG. 2D, userdata 260 is first tunneled between MCD 116 and SGSN 206 in a SubNetwork(SN)-UNITDATA message 262. The user data is then tunneled between SGSN206 and GGSN 208 in a GPRS Tunneling Protocol (GTP) Tunneling-PacketData Unit (T-PDU) message 264. Thereafter, GGSN 208 extracts the userdata 266 and sends it to the external packet data network.

From the foregoing Description, it can be appreciated that varioussignaling procedures are executed pursuant to activating PDP contexts ina wireless packet data service network such as the GPRS-based network202. Further, the manner and mode of the signaling behavior in thenetwork can be dependent on the state and condition of the network,e.g., availability of resources, signaling load, congestion, integrityof the physical plant, et cetera. Accordingly, the network managementinfrastructure is operable to issue a number of cause codes, whichsignify different network responses based on network conditions as wellas MCD-related information (e.g., the network is busy, invalid APNentry, GGSN is out of order, subscriber in default or unauthenticated,et cetera) that can impact a PDP activation procedure initiated by amobile device.

FIG. 3 depicts an exemplary list of cause codes operable with thewireless packet data service network shown in FIG. 2 in servicing amobile communications device according to one embodiment. As set forthin table 300, a cause code (CC) column 302 shows a plurality of causecodes, each with a corresponding entry in a related column 304 thatprovides an explanation of the CC. For example, upon receipt of anActivate PDP Context Request message the network may reject theMCD-initiated context activation by sending an Activate PDP ContextReject message to the MCD that includes a CC #26 (which may be embodiedas an n-bit integer) to indicate insufficient resources. Similarly, a CC#29 may be issued if user authentication has failed. Other CC entries ofthe table 300 are likewise operable to indicate corresponding networkresponses.

As alluded to in the Background section of the present patentapplication, when a data-centric mobile device continues to retryestablishing a data session with the network upon receiving certaincause codes, e.g., indicating failure of a PDP context, itsretransmission logic keeps sending signaling messages towards thenetwork, thereby increasing the signaling load therein. In accordancewith the teachings of the present patent application, a scheme isprovided wherein the data session retry mechanism of the mobile deviceis customized based on the cause code functionality so as to reduce suchsignaling load in the network.

FIG. 4 depicts an exemplary structure 400 for mapping cause codes of awireless packet data service network to a flag or indicium relating to amobile communications device's data session retry mechanism. In essence,a subset of the cause codes associated with a carrier network may beidentified as “critical” cause codes that are mapped to a “NO RETRY”indicium to signify that the retransmission logic of the data sessionretry mechanism be disabled when such a cause code is received from thenetwork. In one embodiment, the structure 400 may be provided as aconfigurable resource file associated with a library that is integratedwithin the mobile device such as MCD 116. In another embodiment, theconfigurable library/structure 400 may be provisioned as part of acarrier network's infrastructure, e.g., associated with a GGSN.

As illustrated in FIG. 4, a CC column 404 is provided on acarrier-by-carrier basis identifying various critical codes for thecarriers in a carrier column 402. In a retry mechanism flag column 406,each CC is marked with a suitable indicium that indicates whether or notthe data session retry mechanism is to be disabled. It should beappreciated that such data may also be configured on a mobilecommunications device by mobile communications device basis. As will bedescribed in detail hereinbelow, an MCD's communications transportprotocol stack is operable to query the structure 400 in order tocustomize its retransmission logic, depending on the status of a new PDPcontext activation or an existing PDP context.

FIG. 5 depicts a software architectural view of a mobile communicationsdevice operable to customize its data session retry mechanism accordingto one embodiment. A multi-layer transport stack (TS) 506 is operable toprovide a generic data transport protocol for any type of corporatedata, including email, via a reliable, secure and seamless continuousconnection to a wireless packet data service network. As illustrated inthe embodiment of FIG. 5, an integration layer 504A is operable as aninterface between the MCD's radio layer 502 and the transport stack 506.Likewise, another integration layer 504B is provided for interfacingbetween the transport stack 506 and the user applications 507 supportedon the MCD, e.g., email 508, calendar/scheduler 510, contact management512 and browser 514. Although not specifically shown, the transportstack 506 may also be interfaced with the MCD's operating system. Inanother implementation, the transport stack 506 may be provided as partof a data communications client module operable as a host-independentvirtual machine on a mobile device.

The bottom layer (Layer 1) of the transport stack 506 is operable as aninterface to the wireless network's packet layer. Layer 1 handles basicservice coordination within the exemplary network environment 100 shownin FIG. 1. For example, when an MCD roams from one carrier network toanother, Layer 1 verifies that the packets are relayed to theappropriate wireless network and that any packets that are pending fromthe previous network are rerouted to the current network. The top layer(Layer 4) exposes various application interfaces to the servicessupported on the MCD. The remaining two layers, Layer 2 and Layer 3, areresponsible for datagram segmentation/reassembly and security,compression and routing, respectively.

A configurable CC resource file 516 provided as part of the softwareenvironment, is disposed in operable communication with the transportstack 506 as well as the MCD's radio layer 502. In one embodiment, theCC resource file 516 may comprise a query-able library structure such asthe embodiment described above in reference to FIG. 4, which includesappropriate mapping between critical cause codes and the MCD's datasession retry mechanism. The contents of the library structure may bedynamically configured upon instantiation of the CC resource file 516.The transport stack 506 is operable to access and interrogate the CCresource library under suitable conditions when the retransmission logicof the MCD's data session retry mechanism is invoked. Also, the flagdescriptor (i.e., “Retry”/“No Retry”) may be passed to the integrationlayer between the user interface and the radio, where the integrationlayer manages the retry mechanism.

FIG. 6 depicts a flowchart of an embodiment for customizing data sessionretry operations in a mobile communications device. Upon detecting bythe transport stack of the MCD that a PDP context has failed to beestablished or is lost (e.g., because the device is out of coveragearea, the PDP context is torn down because of a timeout, et cetera)(block 602), a CC resource file structure/library is queried by thetransport stack (block 604). In one implementation, the transport stackmay query the structure/library prior to invoking the MCD'sretransmission logic or may wait until after a few retransmissionattempts have been made. A determination is made if the CC issued by thenetwork is a critical cause code mapped to a “NO RETRY” indiciumrelating to the MCD's data session retry mechanism (block 606). If not,the retransmission logic of the MCD's data session retry mechanismcontinues to attempt establishing a PDP context (block 608). Otherwise,the data session retry mechanism is disabled or deactivated (block 610).By way of an exemplary implementation, the data session retry mechanismmay be deactivated until the CC structure/library (which has access tothe radio layer as an observer) resolves that the retry mechanism may bere-activated.

FIG. 7 depicts a block diagram of a mobile communications deviceoperable to customize its data session retry mechanism according to oneembodiment. It will be recognized by those skilled in the art uponreference hereto that although an embodiment of MCD 116 may comprise anarrangement similar to one shown in FIG. 7, there can be a number ofvariations and modifications, in hardware, software or firmware, withrespect to the various modules depicted. Accordingly, the arrangement ofFIG. 7 should be taken as illustrative rather than limiting with respectto the embodiments of the present patent application. A microprocessor702 providing for the overall control of an embodiment of MCD 116 isoperably coupled to a communication subsystem 704 which includes areceiver 708 and transmitter 714 as well as associated components suchas one or more local oscillator (LO) modules 710 and a processing modulesuch as a digital signal processor (DSP) 712. As will be apparent tothose skilled in the field of communications, the particular design ofthe communication module 704 may be dependent upon the communicationsnetwork with which the mobile device is intended to operate. In oneembodiment, the communication module 704 is operable with both voice anddata communications. Regardless of the particular design, however,signals received by antenna 706 through BS 114 are provided to receiver708, which may perform such common receiver functions as signalamplification, frequency down conversion, filtering, channel selection,analog-to-digital (A/D) conversion, and the like. Similarly, signals tobe transmitted are processed, including modulation and encoding, forexample, by DSP 712, and provided to transmitter 714 fordigital-to-analog (D/A) conversion, frequency up conversion, filtering,amplification and transmission over the air-radio interface via antenna716.

Microprocessor 702 also interfaces with further device subsystems suchas auxiliary input/output (I/O) 718, serial port 720, display 722,keyboard 724, speaker 726, microphone 728, random access memory (RAM)730, a short-range communications subsystem 732, and any other devicesubsystems generally labeled as reference numeral 733. To controlaccess, a Subscriber Identity Module (SIM) or Removable User IdentityModule (RUIM) interface 734 is also provided in communication with themicroprocessor 702. In one implementation, SIM/RUIM interface 734 isoperable with a SIM/RUIM card having a number of key configurations 744and other information 746 such as identification and subscriber-relateddata.

Operating system software and transport stack software may be embodiedin a persistent storage module (i.e., non-volatile storage) such asFlash memory 735. In one implementation, Flash memory 735 may besegregated into different areas, e.g., storage area for computerprograms 736 as well as data storage regions such as device state 737,address book 739, other personal information manager (PIM) data 741, andother data storage areas generally labeled as reference numeral 743.Additionally, a CC resource file structure 748 (e.g., along with alibrary) may be provided as part of the persistent storage for storing acarrier-specific CC map in accordance with the teachings of the presentpatent application for customization of the MCD's data session retrymechanism.

It is believed that the operation and construction of the embodiments ofthe present patent application will be apparent from the DetailedDescription set forth above. While the exemplary embodiments shown anddescribed may have been characterized as being preferred, it should bereadily understood that various changes and modifications could be madetherein without departing from the scope of the present invention as setforth in the following claims.

What is claimed is:
 1. A method, comprising: after an attempt by amobile communications device to make its presence known has beenaccepted by a carrier of a wireless network: receiving, at the mobilecommunications device and from the wireless network, a retryconfiguration associated with a cause code, the retry configurationindicating whether a data session retry mechanism is to be disabled; inresponse to sending a request for a data session with a node, receiving,at the mobile communications device, a message comprising a rejection ofthe request for activation of the data session, the message comprisingthe cause code, wherein the data session allows data exchange withpackets via the wireless network; and in response to the retryconfiguration associated with the cause code indicating that the datasession retry mechanism is to be disabled, disabling, by the mobilecommunications device, a second request for activation of the datasession with the node, wherein the retry configuration is configured bythe carrier of the wireless network.
 2. The method of claim 1, furthercomprising: receiving a second retry configuration associated with thecause code indicating that the data session retry mechanism is to beenabled; and in response to the second retry configuration associatedwith the cause code indicating that the data session retry mechanism isto be enabled, enabling, by the mobile communications device, a thirdrequest for activation of the data session with the node.
 3. The methodof claim 1, wherein the mobile communications device making its presenceknown comprises performing an attachment procedure.
 4. The method ofclaim 1, wherein the retry configuration associated with the cause codeis stored in a cause code resource file at the mobile communicationsdevice, and the cause code resource file stores a second retryconfiguration associated with a second cause code configured by thecarrier.
 5. The method of claim 4, wherein the cause code resource filestores a third retry configuration associated with the cause codeconfigured by a second carrier of the wireless network.
 6. The method ofclaim 1, wherein the wireless network comprises at least one of aGeneral Packet Radio Service (GPRS) network, an Enhanced Data Rates forGlobal System for Mobile Communications (GSM) Evolution (EDGE) network,a 3rd Generation (3G) network, an Integrated Digital Enhanced Network(IDEN), or a Code Division Multiple Access (CDMA) network.
 7. The methodof claim 1, wherein activation of the data session includes activationof a packet data protocol (PDP) context.
 8. A mobile communicationsdevice, comprising: a memory; and at least one hardware processorcommunicatively coupled with the memory and configured to perform amethod comprising: after an attempt by a mobile communications device tomake its presence known has been accepted by a carrier of a wirelessnetwork: receiving, at the mobile communications device and from thewireless network, a retry configuration associated with a cause code,the retry configuration indicating whether a data session retrymechanism is to be disabled; in response to sending a request for a datasession with a node, receiving, at the mobile communications device, areject message comprising a rejection of the request for activation ofthe data session, the message comprising the cause code, wherein thedata session allows data exchange with packets via the wireless network;and in response to the retry configuration associated with the causecode indicating that the data session retry mechanism is to be disabled,disabling, by the mobile communications device, a second request foractivation of the data session with the node, wherein the retryconfiguration is configured by the carrier of the wireless network. 9.The mobile communications device of claim 8, wherein the method furthercomprises: receiving a second retry configuration associated with thecause code indicating that the data session retry mechanism is to beenabled; and in response to the second retry configuration associatedwith the cause code indicating that the data session retry mechanism isto be enabled, enabling, by the mobile communications device, a thirdrequest for activation of the data session with the node.
 10. The methodof claim 4, wherein the cause code resource file indicates anassociation among a plurality of carriers, a plurality of cause codes,and a plurality of retry mechanism flags indicating whether a datasession retry mechanism is to be disabled.
 11. The method of claim 10,further comprises: comparing the cause code in the message with theretry configuration in the cause code resource file stored at the mobilecommunications device; and determining the retry configurationassociated with the cause code indicating that the data session retrymechanism is to be disabled by determining that the cause code in themessage matches the cause code associated with the retry configurationin the cause code resource file that indicates the data session retrymechanism is to be disabled.
 12. The mobile communications device ofclaim 8, wherein the retry configuration associated with the cause codeis stored in a cause code resource file at the mobile communicationsdevice, and the cause code resource file stores a second retryconfiguration associated with a second cause code configured by thecarrier.
 13. The mobile communications device of claim 12, wherein thecause code resource file stores a third retry configuration associatedwith the cause code configured by a second carrier of the wirelessnetwork.
 14. The mobile communications device of claim 8, wherein thewireless network comprises at least one of a General Packet RadioService (GPRS) network, an Enhanced Data Rates for Global System forMobile Communications (GSM) Evolution (EDGE) network, a 3rd Generation(3G) network, an Integrated Digital Enhanced Network (IDEN), or a CodeDivision Multiple Access (CDMA) network.
 15. The mobile communicationsdevice of claim 8, wherein activation of the data session includesactivation of a packet data protocol (PDP) context.
 16. A non-transitorycomputer-readable medium containing instructions which, when executed,cause a mobile communications device to perform operations comprising:after an attempt by a mobile communications device to make its presenceknown has been accepted by a carrier of a wireless network: receiving,at the mobile communications device and from the wireless network, aretry configuration associated with a cause code, the retryconfiguration indicating whether a data session retry mechanism is to bedisabled; in response to sending a request for a data session with anode, receiving, at the mobile communications device, a messagecomprising a rejections of the request for activation of the datasession, the message comprising the cause code, wherein the data sessionallows data exchange with packets via the wireless network; and inresponse to the retry configuration associated with the cause codeindicating that the data session retry mechanism is to be disabled,disabling, by the mobile communications device, a second request foractivation of the data session with the node, wherein the retryconfiguration is configured by the carrier of the wireless network. 17.The non-transitory computer-readable medium of claim 16, wherein theoperations further comprise: receiving a second retry configurationassociated with the cause code indicating that the data session retrymechanism is to be enabled; and in response to the second retryconfiguration associated with the cause code indicating that the datasession retry mechanism is to be enabled, enabling, by the mobilecommunications device, a third request for activation of the datasession with the node.
 18. The non-transitory computer-readable mediumof claim 16, wherein the retry configuration associated with the causecode is stored in a cause code resource file at the mobilecommunications device, and the cause code resource file stores a secondretry configuration associated with a second cause code configured bythe carrier.
 19. The non-transitory computer-readable medium of claim18, wherein the cause code resource file stores a third retryconfiguration associated with the cause code configured by a secondcarrier of the wireless network.
 20. The non-transitorycomputer-readable medium of claim 16, wherein the wireless networkcomprises at least one of a General Packet Radio Service (GPRS) network,an Enhanced Data Rates for Global System for Mobile Communications (GSM)Evolution (EDGE) network, a 3rd Generation (3G) network, an IntegratedDigital Enhanced Network (IDEN), or a Code Division Multiple Access(CDMA) network.